Microsoft reveals software defect behind global outage that left 80% of gateway servers unresponsive

The outage disrupted Outlook and other Microsoft 365 services, affecting businesses and airlines in India and several other countries.

Microsoft is cutting 4,800 jobs, including 1,600 positions at Xbox, as part of a major restructuring. Photo: Unsplash/BoliviaInteligente
13 min read  |  Published: 16 Nov 2026

New Delhi: More than 80 per cent of servers behind Microsoft's networking gateway were unresponsive at the peak of last week's global outage of Outlook and other Microsoft 365 services, the company has said, blaming a hidden software defect introduced in July.

Three factors combined to cause the outage of the networking gateway that sits in front of many Microsoft 365 services, Charles Lamanna, Microsoft's executive vice-president of Copilot, Agents and Platform, said in a post on X on Monday.

“We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations,” he said.

More details on the root cause can be found in the Microsoft 365 Admin center, and an abridged version can be found below. We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations. The incident on Thursday, November 12th, 2026, was caused by three main factors that together caused a global outage for the networking gateway that fronts many Microsoft 365 services.First, a latent defect caused servers to become overwhelmed and unresponsive under certain load conditions. This was due to lock contention inside an internal process which caused the machine to become unavailable. This defect was the result of a fix that was prepared specifically for Microsoft 365 networking gateway servers; neither the underlying defect nor the fix applies to broader Windows deployments.The initial change in behavior first started deployment in July of this year. The update went through safe deployment and saturated globally over several weeks, during which time no issues were observed. For more than three months, the change was deployed worldwide without impact.Our normal load testing did not detect the latent issue because the different traffic and SKU mix used in our test labs. The contention issue is worsened on machines with more cores and newer hardware; whereas our load testing tended to focus on our weaker hardware SKUs with fewer cores.Second, a surge in load increased the likelihood for the networking gateways to encounter the contention. Within Microsoft 365, we maintain two independent and heterogenous network gateway systems designed for isolation and high availability. This allows many Microsoft 365 services to fail to/from them during outages or disruptions. Approximately fifteen hours before the outage, Teams failed over from the alternative networking gateway to the ‘primary’ gateway that also supports Exchange Online. This increased the load on the networking gateway and changed its traffic patterns. This type of failover is part of normal operations and is integral to standard Microsoft resiliency efforts.Third, at the same time, nearly 14% of server capacity for the networking gateway was out of service due to an unrelated issue from the previous day. This server capacity was on track to be returned to active service through routine maintenance and health processes. The service had sufficient capacity headroom, so the reduction in server capacity had no impact on its own.Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States.When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient. However, the redirected traffic increased the likelihood for the same problem to occur on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive.Normally, the network gateway is composed of thousands of ‘capacity units’ which represent shards of capacity, hardware, and networking infrastructure. These ‘capacity units’ are then organized into regions. In this case, due to a separate issue, the normal bulkheads between these different partitions did not stop the cascading failure. This is what allowed the impact to spread across our network gateway infrastructure globally.Several services like Teams, OneDrive, SharePoint, and Office apps failed out of the faulty network gateway infrastructure. That is why those services were restored earlier, with Teams chats and meetings functioning without issue for most of the outage. But not all services, like Exchange Online, can fail out of this network gateway.Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again. Our normally automated recovery processes were not designed to restore service from this broad unresponsive state. Additionally, since the main code defect was a latent bug from several months previous, our normal rollback, flighting, and feature flags were unable to quickly revert the change.After engineers confirmed the defect as the cause, we developed an update that returned the code path to the previously known good state. To effectively apply this fix, and to slowly bring the service online again, we took groups of servers out of service, applied the change, and restarted them before returning them to service. This process was carefully applied to large quantities of infrastructure at a time (e.g. 50%+ of a region).The final Post-Incident Review (PIR) will provide more details later this week.

The first factor was a latent defect that caused servers to become overwhelmed and unresponsive under certain load conditions. It originated from a fix prepared specifically for Microsoft 365 networking gateway servers and does not apply to broader Windows deployments, Lamanna said.

The initial change began rolling out in July and remained in place worldwide for more than three months without any impact, he said. The company's load testing did not catch the problem because the tests focused on weaker hardware, while the defect is worse on newer machines with more processing cores.

Second, about 15 hours before the outage, Microsoft Teams shifted from an alternative gateway to the primary gateway that also supports Exchange Online, the company's email platform. This increased the load on that gateway and changed its traffic patterns. Lamanna said such a shift is part of normal operations.

Third, nearly 14 per cent of the gateway's server capacity was out of service at the time because of an unrelated issue from the previous day.

Taken together, the higher load and reduced capacity caused the gateway to hit the latent bug from July, and requests built up until servers ultimately stopped responding. This happened during the peak traffic period in the United States, he said.

“When servers lose connectivity, our traffic management systems automatically route users to other healthy endpoints. This happens often and is critical to avoiding any interruption due to hardware, software, or network defects and is normally what makes the service resilient.”

“However, the redirected traffic increased the likelihood of the same problem occurring on the remaining endpoints. This caused a cascading failure from server to server as the same amount of load was spread across fewer servers. In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80 per cent of servers were unresponsive," Lamanna said.

The safeguards that normally separate different parts of the gateway did not stop the failure because of a separate issue, which allowed the impact to spread globally, he added.

Services such as Teams, OneDrive, SharePoint and Office apps were able to move off the faulty gateway and were restored earlier, with Teams chats and meetings working for most of the outage. Exchange Online cannot do so, Lamanna said.

Recovery took longer than usual because servers returning to service were immediately overwhelmed by waiting traffic and became unresponsive again.

The company's automated recovery processes were not designed for such a broad failure, and since the defect was several months old, its usual methods could not quickly reverse the change, he said.

Engineers then developed an update that returned the code to its previous state. They took groups of servers out of service, applied the change and restarted them before bringing them back.

A final post-incident review with more details will be provided later this week, Lamanna said.

The outage, which began late on Thursday, affected Indian airlines, financial services firms and businesses. Domestic airlines IndiGo, Air India and Akasa Air reported disruptions to email-based customer support, affecting their ability to receive or respond to some passenger queries. Air India temporarily rerouted email services to ensure customer communications continued reaching the airline, while flight operations were not reported to have been affected.

Financial services firms also faced difficulties accessing research reports and conducting client interactions.

The disruption primarily affected Microsoft 365 features that interact with Exchange Online, the company's cloud-based email platform. Users were unable to access mailboxes through Outlook on the web and desktop applications, and email delivery was delayed.

At its peak, the outage generated more than 1.3 lakh reports of Outlook problems on the outage-tracking website Downdetector, with disruptions reported across 72 to 74 countries.

To advertise here,contact us